At 23:48 +0300 on 01/07/1999, Collin F. Lynch wrote:
> I'm having the peculiar problem That Postgres Seems unable to deal
>with microseconds in a time field. I have the field defined as type time,
>and postgres accepts input of the form 12:22:13.41 but appears to ose the
>microseconds withn the database itself?
It's just the output of the time datatype. This datatype is a bit odd. You
can see that the microseconds are kept. Compare:
testing=> select '12:05:11.04'::time;
?column?
--------
12:05:11
(1 row)
testing=> select datetime( 'today', '12:05:11.04'::time );
datetime
-------------------------------
Sun Jul 04 12:05:11.04 1999 IDT
(1 row)
So you see, the milliseconds are actually. It's just that it didn't show in
the normal display form.
The TIME datatype is supposed to be compatible with SQL92, but it's, well,
not exactly. Anyway, the default precision for time is 0, that is, no
fractions of seconds unless stated so explicitly. However, since it stores
milliseconds, it defies that definition.
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma